MySQL 8.0 is scheduled for End of Life (EOL) in April 2026. In line with this milestone, we previously announced in this Oracle blog post that all existing MySQL HeatWave instances running version 8.0 would be automatically upgraded to the latest supported 8.4 release after April 2026.
However, understanding the operational realities and planning cycles of our customers, we are extending support for MySQL 8.0 instances in MySQL HeatWave until April 2027. This extension allows organizations additional time to communicate, coordinate, and execute upgrade plans in partnership with Oracle’s sales and support teams. During this extension, existing 8.0 instances will remain fully functional and receive critical security patches, ensuring business continuity and data protection as you transition to newer versions.
What does the MySQL 8.0 EOL extension mean?
1. Current 8.0 MySQL HeatWave instances remain operational and secure
Existing MySQL HeatWave instances running a version lower than 8.0.46 will continue to operate. In the maintenance cycle in June 2026, all instances running 8.0 will be automatically upgraded to 8.0.46. This measure ensures that all supported 8.0 instances benefit from critical security and stability updates until the final transition to newer MySQL versions. Oracle will apply only essential security patches to both the OS and MySQL database until April 2027. This approach ensures your data remains safe while you prepare for an upgrade.
2. New 8.0 Instances and Major Operations Restricted
To support a consistent upgrade path, certain actions involving MySQL 8.0 are no longer allowed:
- Creating a new 8.0 instance is not permitted.
- Changing your instance shape (e.g., from MySQL.2 to MySQL.4) is not allowed for instances running 8.0 version.
- Restoring backups to create new 8.0 instances triggers an automatic upgrade—any restored backup will result in an instance running the latest MySQL 8.4 version.
- Adding 8.0 based read replicas to any DB systems is not supported.
3. Automatic Upgrades Post April 2027
After April 2027, any remaining MySQL HeatWave 8.0 instances will be automatically upgraded to MySQL 8.4 LTS during their next maintenance window, following Oracle Cloud Hosting and Delivery policies (see details).
How is Oracle Supporting Customers?
Early Notifications and Guidance
- Console Notifications: You’ll see a prominent banner in the Oracle Cloud Console, reminding you of the upcoming EOL and linking to resources for seamless upgrades.
- Direct Communications: Regular Cloud Notification (CN) will alert affected customers. Messages will be sent monthly from February to April, quarterly in August and January, then monthly from February to April as the timeline progresses.
Comprehensive Self-Service and Support
- Knowledge Articles & FAQs: Oracle provides up-to-date documentation to support your transition:
What Should Customers Do Next?
- Review and Plan: Collaborate with your Oracle sales and support teams to develop an upgrade plan ahead of the April 2027 automatic upgrade window.
- Stay Informed: Watch for notifications in the console and via email and review the resources linked above for details.
- Act Early: Proactively upgrading to MySQL 8.4 ensures continued access to the latest features and stability.
Summary
Extending the EOL for MySQL 8.0 in MySQL HeatWave to April 2027 offers plenty of time for thoughtful planning and execution of upgrades. Oracle will support this transition with ongoing security, transparent communication, and dedicated upgrade resources. For more information and frequent updates, refer to the provided KM articles or reach out to your Oracle support representative.
